Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb8244d91a6755ac90700670d8e9ff5aba3152fed8213e5b235cd862ebcc3a41

Tx prefix hash: 1aa4b0767b7b80ec2d3e29a64f721d69ea7fba41a4911d636cfd12e9a73e1333
Tx public key: 1c84e9c35948b8df93935ccd2191aac2f29dbc4f8dd17d0736e1fdd96b92aca3
Timestamp: 1610033020 Timestamp [UCT]: 2021-01-07 15:23:40 Age [y:d:h:m:s]: 04:052:20:03:54
Block: 175830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1053218 RingCT/type: yes/0
Extra: 011c84e9c35948b8df93935ccd2191aac2f29dbc4f8dd17d0736e1fdd96b92aca3021100000f26b9b01d0b000000000000000000

1 output(s) for total of 160.476114411000 dcy

stealth address amount amount idx
00: 57d950346d64dfa6ba2941fb0024ad719e00a8f1b26fec5d3e82f402eb559e6a 160.476114411000 336238 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": 175840, "vin": [ { "gen": { "height": 175830 } } ], "vout": [ { "amount": 160476114411, "target": { "key": "57d950346d64dfa6ba2941fb0024ad719e00a8f1b26fec5d3e82f402eb559e6a" } } ], "extra": [ 1, 28, 132, 233, 195, 89, 72, 184, 223, 147, 147, 92, 205, 33, 145, 170, 194, 242, 157, 188, 79, 141, 209, 125, 7, 54, 225, 253, 217, 107, 146, 172, 163, 2, 17, 0, 0, 15, 38, 185, 176, 29, 11, 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