Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb9d0cc459428cb953e3b8833a6f76f9f446a9626702227df50b6a05d383f653

Tx prefix hash: ee6cc35258ee549af7fd36740e3cabf8ab4327ed5b5d48b9a50182030ac6d83d
Tx public key: b0b455471f51ceb09a7f8ae8d8bc9867c56cfaa0554877003617e033375d3016
Timestamp: 1705496005 Timestamp [UCT]: 2024-01-17 12:53:25 Age [y:d:h:m:s]: 01:090:19:46:15
Block: 937286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326014 RingCT/type: yes/0
Extra: 01b0b455471f51ceb09a7f8ae8d8bc9867c56cfaa0554877003617e033375d301602110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b96bc2c29dd447a0d99c3bbd257e6c8eb5b31e20e57f17d998391f4ed2d040b6 0.600000000000 1395336 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": 937296, "vin": [ { "gen": { "height": 937286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b96bc2c29dd447a0d99c3bbd257e6c8eb5b31e20e57f17d998391f4ed2d040b6" } } ], "extra": [ 1, 176, 180, 85, 71, 31, 81, 206, 176, 154, 127, 138, 232, 216, 188, 152, 103, 197, 108, 250, 160, 85, 72, 119, 0, 54, 23, 224, 51, 55, 93, 48, 22, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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