Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be75c19a24b3644e13436c49c5c0412e57336de6f6d8032ad53fbc7cf205d02b

Tx prefix hash: b6ec6b2f7dd7b44f87327f06d59fedbc1af691d82fd03ccf4a033862b500bf55
Tx public key: 441919cead2e6b693937fea1cc3afa3d2b8c0a974835b7fb03ddef241d405c4e
Timestamp: 1750028637 Timestamp [UCT]: 2025-06-15 23:03:57 Age [y:d:h:m:s]: 00:151:14:36:54
Block: 1305848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106130 RingCT/type: yes/0
Extra: 01441919cead2e6b693937fea1cc3afa3d2b8c0a974835b7fb03ddef241d405c4e02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 925190566760ec65dbf0ce424a6e6594dd05fe5b84a8fe6dcd736a2cf3e2e40f 0.600000000000 1793451 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": 1305858, "vin": [ { "gen": { "height": 1305848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "925190566760ec65dbf0ce424a6e6594dd05fe5b84a8fe6dcd736a2cf3e2e40f" } } ], "extra": [ 1, 68, 25, 25, 206, 173, 46, 107, 105, 57, 55, 254, 161, 204, 58, 250, 61, 43, 140, 10, 151, 72, 53, 183, 251, 3, 221, 239, 36, 29, 64, 92, 78, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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