Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13f80bb8c2a6afe5920f3137ee12ac5fbc96a95adc47a5abc700beeae2aa514c

Tx prefix hash: 51dc0594adff92a828a259687d94382b48ec25bdaeb208906c36cabe2380e953
Tx public key: 2769307d3dd09cf208f6c5be96e8850a3c1207d08afc39e248af177b4da58233
Timestamp: 1698236609 Timestamp [UCT]: 2023-10-25 12:23:29 Age [y:d:h:m:s]: 01:084:19:05:42
Block: 877347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321816 RingCT/type: yes/0
Extra: 012769307d3dd09cf208f6c5be96e8850a3c1207d08afc39e248af177b4da5823302110000000533af99f4000000000000000000

1 output(s) for total of 0.760300369000 dcy

stealth address amount amount idx
00: d4f3ffab15411fea316c8571293af2934e839cd59822d5e33f7c8bdc3e15c3a2 0.760300369000 1332721 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": 877357, "vin": [ { "gen": { "height": 877347 } } ], "vout": [ { "amount": 760300369, "target": { "key": "d4f3ffab15411fea316c8571293af2934e839cd59822d5e33f7c8bdc3e15c3a2" } } ], "extra": [ 1, 39, 105, 48, 125, 61, 208, 156, 242, 8, 246, 197, 190, 150, 232, 133, 10, 60, 18, 7, 208, 138, 252, 57, 226, 72, 175, 23, 123, 77, 165, 130, 51, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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