Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635e173cb089bc6d3b894efc850587907ee8ef33fb5a5ba7765da34d0670b323

Tx prefix hash: 967b65c6018ba1205e30e2a00c16350029f38fedc19aa0630843f817e368b55a
Tx public key: 68553e91c7f562db702f00b559ab1068ac8fdc200d978572e7d8960dba6c9a87
Timestamp: 1576424509 Timestamp [UCT]: 2019-12-15 15:41:49 Age [y:d:h:m:s]: 04:338:01:47:34
Block: 27389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127709 RingCT/type: yes/0
Extra: 0168553e91c7f562db702f00b559ab1068ac8fdc200d978572e7d8960dba6c9a870211000000269159db1e000000000000000000

1 output(s) for total of 498.023389114000 dcy

stealth address amount amount idx
00: 5b37fdb4fe65cc3c4c4cae97c28dc2ef71b93bfc9933c544014256282b8a02ac 498.023389114000 45389 of 0

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": 27399, "vin": [ { "gen": { "height": 27389 } } ], "vout": [ { "amount": 498023389114, "target": { "key": "5b37fdb4fe65cc3c4c4cae97c28dc2ef71b93bfc9933c544014256282b8a02ac" } } ], "extra": [ 1, 104, 85, 62, 145, 199, 245, 98, 219, 112, 47, 0, 181, 89, 171, 16, 104, 172, 143, 220, 32, 13, 151, 133, 114, 231, 216, 150, 13, 186, 108, 154, 135, 2, 17, 0, 0, 0, 38, 145, 89, 219, 30, 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