Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16d308e998567f07daca445b0c8d1de9d0dac7aa607ba7963d3a892f5854850

Tx prefix hash: f01758b9e4001e35492c0f083987449ce3ee1d8b91115528f15c7f499e756abb
Tx public key: 1682d6f9fb9241defd9bf5ac8dded054c0ecfb1046d60ebfd02213468aa7c39e
Timestamp: 1648659271 Timestamp [UCT]: 2022-03-30 16:54:31 Age [y:d:h:m:s]: 02:272:01:12:50
Block: 469707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714040 RingCT/type: yes/0
Extra: 011682d6f9fb9241defd9bf5ac8dded054c0ecfb1046d60ebfd02213468aa7c39e021100000011bf7ee4e7000000000000000000

1 output(s) for total of 17.047707068000 dcy

stealth address amount amount idx
00: 47732fb93375f425ae26554cb239e816c5706f0152cdc50206d6e2f2d52749c8 17.047707068000 888705 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": 469717, "vin": [ { "gen": { "height": 469707 } } ], "vout": [ { "amount": 17047707068, "target": { "key": "47732fb93375f425ae26554cb239e816c5706f0152cdc50206d6e2f2d52749c8" } } ], "extra": [ 1, 22, 130, 214, 249, 251, 146, 65, 222, 253, 155, 245, 172, 141, 222, 208, 84, 192, 236, 251, 16, 70, 214, 14, 191, 208, 34, 19, 70, 138, 167, 195, 158, 2, 17, 0, 0, 0, 17, 191, 126, 228, 231, 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