Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16f2a257010883224674cf15bca3144ecfe52ebbe2399d0a38f6a97021b0f47

Tx prefix hash: 337bb2092fad6230afddf46d090d3007056d0baa4a0f12addb34be374afb407d
Tx public key: 94a3ee70ac638d7d3f1956ab8d5181cef38f77120f5aecc4b779f2aa91ba194b
Timestamp: 1576467074 Timestamp [UCT]: 2019-12-16 03:31:14 Age [y:d:h:m:s]: 05:024:12:57:01
Block: 27890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164391 RingCT/type: yes/0
Extra: 0194a3ee70ac638d7d3f1956ab8d5181cef38f77120f5aecc4b779f2aa91ba194b0211000000018a2ee0d9000000000000000000

1 output(s) for total of 496.140517278000 dcy

stealth address amount amount idx
00: 91554c93589e643961d992d451370b3c461bb798bcc6b3f41858802a2d22a752 496.140517278000 46068 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": 27900, "vin": [ { "gen": { "height": 27890 } } ], "vout": [ { "amount": 496140517278, "target": { "key": "91554c93589e643961d992d451370b3c461bb798bcc6b3f41858802a2d22a752" } } ], "extra": [ 1, 148, 163, 238, 112, 172, 99, 141, 125, 63, 25, 86, 171, 141, 81, 129, 206, 243, 143, 119, 18, 15, 90, 236, 196, 183, 121, 242, 170, 145, 186, 25, 75, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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