Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc7bab3b7492361514c707586712c1bcbe8101fe2fdadd9c0c85d50cebc20f44

Tx prefix hash: d3ea7264f62d6c61ca106dc556b6c142d9d37ec61ba0b582b5d37e434e75f2a1
Tx public key: 2b9b7b6b3f801af6271a374b86ebbdd11766f0b11ba2efa9c382be2af7e15ce5
Timestamp: 1736886220 Timestamp [UCT]: 2025-01-14 20:23:40 Age [y:d:h:m:s]: 00:155:03:21:37
Block: 1197407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110568 RingCT/type: yes/0
Extra: 012b9b7b6b3f801af6271a374b86ebbdd11766f0b11ba2efa9c382be2af7e15ce5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f415446d1f8116a14f287abb4b568b75fe740be5df003abb96cc26186e563717 0.600000000000 1684014 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": 1197417, "vin": [ { "gen": { "height": 1197407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f415446d1f8116a14f287abb4b568b75fe740be5df003abb96cc26186e563717" } } ], "extra": [ 1, 43, 155, 123, 107, 63, 128, 26, 246, 39, 26, 55, 75, 134, 235, 189, 209, 23, 102, 240, 177, 27, 162, 239, 169, 195, 130, 190, 42, 247, 225, 92, 229, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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