Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3690950f49152e4e94e9938979398706bc4256df7ad7bc33ef93929d6f85cf0e

Tx prefix hash: 794d9b071cc9f70ceeeb404457201f6f8610b3fa814e639ffa6c5f7a4f1ce1b7
Tx public key: 90712e390ce82999a61f31f4e9af01ca77306fe262f4e07cf3acc766c3870bf4
Timestamp: 1756290962 Timestamp [UCT]: 2025-08-27 10:36:02 Age [y:d:h:m:s]: 00:118:13:41:19
Block: 1355505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84710 RingCT/type: yes/0
Extra: 0190712e390ce82999a61f31f4e9af01ca77306fe262f4e07cf3acc766c3870bf4021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 531704c4f90053013f843020f788ef902ea6360a932c691f5e67d1ecaaa0c8e1 0.600000000000 1843506 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": 1355515, "vin": [ { "gen": { "height": 1355505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "531704c4f90053013f843020f788ef902ea6360a932c691f5e67d1ecaaa0c8e1" } } ], "extra": [ 1, 144, 113, 46, 57, 12, 232, 41, 153, 166, 31, 49, 244, 233, 175, 1, 202, 119, 48, 111, 226, 98, 244, 224, 124, 243, 172, 199, 102, 195, 135, 11, 244, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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