Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de18b99704273c5653ab2cb17671db4cadf5a6928968c62c4c9b5e45043f50e5

Tx prefix hash: 1cf07ca15c179e4ab2ff22a10fdc59ef71b0dc619ec1b93b279ffb097cb1d150
Tx public key: de136ffb29893dac986cbf13f168585c232f77e3b27aa0f287f2ac37da16c81b
Timestamp: 1702399099 Timestamp [UCT]: 2023-12-12 16:38:19 Age [y:d:h:m:s]: 01:150:11:22:06
Block: 911658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368682 RingCT/type: yes/0
Extra: 01de136ffb29893dac986cbf13f168585c232f77e3b27aa0f287f2ac37da16c81b02110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0121e511c0a35eb8df2c3950d645aacd0d3f8dd51fda994b09c4b6c5893c19d4 0.600000000000 1368872 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": 911668, "vin": [ { "gen": { "height": 911658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0121e511c0a35eb8df2c3950d645aacd0d3f8dd51fda994b09c4b6c5893c19d4" } } ], "extra": [ 1, 222, 19, 111, 251, 41, 137, 61, 172, 152, 108, 191, 19, 241, 104, 88, 92, 35, 47, 119, 227, 178, 122, 160, 242, 135, 242, 172, 55, 218, 22, 200, 27, 2, 17, 0, 0, 0, 2, 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