Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d357c2de653cc58f99521aae2f2ed91ed7005f847945017a2e5f7d581e350be7

Tx prefix hash: 97bd4a43651bc670083160a76c511f687a2ad7b7f1aad5de99013e8cb83df748
Tx public key: 3f0331c7aa473c0db25abba9badbc0671b201eb8ae8a417d40c60ce88d2e5080
Timestamp: 1765728639 Timestamp [UCT]: 2025-12-14 16:10:39 Age [y:d:h:m:s]: 00:007:10:05:47
Block: 1433526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5323 RingCT/type: yes/0
Extra: 013f0331c7aa473c0db25abba9badbc0671b201eb8ae8a417d40c60ce88d2e5080021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7561d2e5e40926e9791b9ea1579de4435e36af73543cb6fda608a08c4309de3 0.600000000000 1922307 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1433536, "vin": [ { "gen": { "height": 1433526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7561d2e5e40926e9791b9ea1579de4435e36af73543cb6fda608a08c4309de3" } } ], "extra": [ 1, 63, 3, 49, 199, 170, 71, 60, 13, 178, 90, 187, 169, 186, 219, 192, 103, 27, 32, 30, 184, 174, 138, 65, 125, 64, 198, 12, 232, 141, 46, 80, 128, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8