Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fb0812ce9487779fa0454085f91eb26847812654d38339c2d3d3823be1403b1

Tx prefix hash: 0cab999d6fbb10512253f1be052ac67e394cccfdbdea1b0d3017a70acee59782
Tx public key: d15976481a99608d29f759c395c6fbdb602d16ced2fb6e5ef5a0a082dd72baf5
Timestamp: 1698573981 Timestamp [UCT]: 2023-10-29 10:06:21 Age [y:d:h:m:s]: 01:213:23:33:07
Block: 880138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413979 RingCT/type: yes/0
Extra: 01d15976481a99608d29f759c395c6fbdb602d16ced2fb6e5ef5a0a082dd72baf5021100000002faf35c9c000000000000000000

1 output(s) for total of 0.744281897000 dcy

stealth address amount amount idx
00: 305d28297d50924c22b1a902605ec6dbe6f1966b042ea6e877af52ff0d6c71a1 0.744281897000 1335684 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": 880148, "vin": [ { "gen": { "height": 880138 } } ], "vout": [ { "amount": 744281897, "target": { "key": "305d28297d50924c22b1a902605ec6dbe6f1966b042ea6e877af52ff0d6c71a1" } } ], "extra": [ 1, 209, 89, 118, 72, 26, 153, 96, 141, 41, 247, 89, 195, 149, 198, 251, 219, 96, 45, 22, 206, 210, 251, 110, 94, 245, 160, 160, 130, 221, 114, 186, 245, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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