Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b214367445c8d8cd63cd4f9fa4c09a0fb782fac8b5d2c669b75d945d11286acd

Tx prefix hash: 5544263bb7efbc29b3effc1acc81d06555be52b08d86e8bb8f3983911b469dee
Tx public key: 45fb82459cb6273b6b753b20a2e536944a274ad0af1ea7edb0551417e0a47718
Timestamp: 1765723058 Timestamp [UCT]: 2025-12-14 14:37:38 Age [y:d:h:m:s]: 00:009:05:10:09
Block: 1433487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6587 RingCT/type: yes/0
Extra: 0145fb82459cb6273b6b753b20a2e536944a274ad0af1ea7edb0551417e0a477180211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df0e9b9a4f4903a577b1d5514c9f36c31b3a342058ed31b253311646c4d5e90a 0.600000000000 1922266 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": 1433497, "vin": [ { "gen": { "height": 1433487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df0e9b9a4f4903a577b1d5514c9f36c31b3a342058ed31b253311646c4d5e90a" } } ], "extra": [ 1, 69, 251, 130, 69, 156, 182, 39, 59, 107, 117, 59, 32, 162, 229, 54, 148, 74, 39, 74, 208, 175, 30, 167, 237, 176, 85, 20, 23, 224, 164, 119, 24, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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