Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c56fbc8412e817aaca4d97793df2743b5927bedd303c1da68120cf3e945de5b

Tx prefix hash: 8d78a855c1fad466f730eed0ae06f955221e4001bfe5ec333bcaf3dd6eea13b3
Tx public key: 1f47cd06433456ae7a2efb56a43ae2b08a7f9d0c80339b9abfbb3218ed763327
Timestamp: 1729071580 Timestamp [UCT]: 2024-10-16 09:39:40 Age [y:d:h:m:s]: 01:022:07:35:55
Block: 1132774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274298 RingCT/type: yes/0
Extra: 011f47cd06433456ae7a2efb56a43ae2b08a7f9d0c80339b9abfbb3218ed7633270211000000093cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32e917ef2e72352bc58eb3031790cd553f5568901e2b7d593e9a3a013f15cdd5 0.600000000000 1615769 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": 1132784, "vin": [ { "gen": { "height": 1132774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32e917ef2e72352bc58eb3031790cd553f5568901e2b7d593e9a3a013f15cdd5" } } ], "extra": [ 1, 31, 71, 205, 6, 67, 52, 86, 174, 122, 46, 251, 86, 164, 58, 226, 176, 138, 127, 157, 12, 128, 51, 155, 154, 191, 187, 50, 24, 237, 118, 51, 39, 2, 17, 0, 0, 0, 9, 60, 208, 252, 6, 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