Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcbe13d19f831917b5ddf5e2525290ee40be698fafb44e6040190bfeea711cdc

Tx prefix hash: f49671ae4fc3b92f445a7a97b038b5fdbaf2ce287547d4d10e9d8b5b3594bd23
Tx public key: 5a43a71602d12ad935346673087895fadcb98de2275e8cbae933f26b802a0e96
Timestamp: 1755742868 Timestamp [UCT]: 2025-08-21 02:21:08 Age [y:d:h:m:s]: 00:090:17:52:08
Block: 1350999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64753 RingCT/type: yes/0
Extra: 015a43a71602d12ad935346673087895fadcb98de2275e8cbae933f26b802a0e960211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93ab2c2efdd5b20302bc29f1cba8ac6c5619585c11e09d605a35ec5fd570a661 0.600000000000 1838946 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": 1351009, "vin": [ { "gen": { "height": 1350999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93ab2c2efdd5b20302bc29f1cba8ac6c5619585c11e09d605a35ec5fd570a661" } } ], "extra": [ 1, 90, 67, 167, 22, 2, 209, 42, 217, 53, 52, 102, 115, 8, 120, 149, 250, 220, 185, 141, 226, 39, 94, 140, 186, 233, 51, 242, 107, 128, 42, 14, 150, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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