Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce9cb92ba51a053fbe4431a4357e4919705f1cbf4507ec7c300385efaba2e837

Tx prefix hash: 77fbfb5d28ada9a4b0c782d8e5a7d468d05056db422b461c003b0d852d1c0279
Tx public key: 0dfbbe90f7a6f18747288c5e2cce01af5139e3bd71408b7f22dff41b1b429547
Timestamp: 1707586864 Timestamp [UCT]: 2024-02-10 17:41:04 Age [y:d:h:m:s]: 01:278:00:24:42
Block: 954634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457481 RingCT/type: yes/0
Extra: 010dfbbe90f7a6f18747288c5e2cce01af5139e3bd71408b7f22dff41b1b4295470211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a520725184f9a457b621c7f94833be0376bfa1b85da79e7d3eadab3bd05355fb 0.600000000000 1413914 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": 954644, "vin": [ { "gen": { "height": 954634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a520725184f9a457b621c7f94833be0376bfa1b85da79e7d3eadab3bd05355fb" } } ], "extra": [ 1, 13, 251, 190, 144, 247, 166, 241, 135, 71, 40, 140, 94, 44, 206, 1, 175, 81, 57, 227, 189, 113, 64, 139, 127, 34, 223, 244, 27, 27, 66, 149, 71, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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