Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0203f60e1ff3de4ccfbee09a1963b967b301a53ab18cf5a1e6048e6fefb8a65a

Tx prefix hash: 795eb3d029e76aaf6f1fe341e2e9454c443683c3447afd11338699975a8f941e
Tx public key: dea63922346629c1b099f1357d8c7877c3c4a08406f112f82aa4c9693e50ab04
Timestamp: 1656861954 Timestamp [UCT]: 2022-07-03 15:25:54 Age [y:d:h:m:s]: 02:273:04:08:25
Block: 535835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 716349 RingCT/type: yes/0
Extra: 01dea63922346629c1b099f1357d8c7877c3c4a08406f112f82aa4c9693e50ab04021100000007a8c141c5000000000000000000

1 output(s) for total of 10.293341046000 dcy

stealth address amount amount idx
00: 436546a0584cee0490acab4303846c70290f1d854b156decb4da1c8c81f09a1a 10.293341046000 965500 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": 535845, "vin": [ { "gen": { "height": 535835 } } ], "vout": [ { "amount": 10293341046, "target": { "key": "436546a0584cee0490acab4303846c70290f1d854b156decb4da1c8c81f09a1a" } } ], "extra": [ 1, 222, 166, 57, 34, 52, 102, 41, 193, 176, 153, 241, 53, 125, 140, 120, 119, 195, 196, 160, 132, 6, 241, 18, 248, 42, 164, 201, 105, 62, 80, 171, 4, 2, 17, 0, 0, 0, 7, 168, 193, 65, 197, 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