Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559ab7474307c87ca2c8edf5c5644fc2b72e49673e131e9a90397c9f893f4b73

Tx prefix hash: 0364ff72aabe7b85fd1f30643887049df68057e1bf9ce6a63f53fac0638dbcec
Tx public key: 514c9eb229f4634c429ab704c086ae020c991bfa11c7b2998a43035ab4e6034d
Timestamp: 1725204210 Timestamp [UCT]: 2024-09-01 15:23:30 Age [y:d:h:m:s]: 00:217:03:41:40
Block: 1100705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155037 RingCT/type: yes/0
Extra: 01514c9eb229f4634c429ab704c086ae020c991bfa11c7b2998a43035ab4e6034d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f321a243cc5ab8de6311aa4335168382951560fa4f810a282e623073bbc4cbf7 0.600000000000 1576684 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": 1100715, "vin": [ { "gen": { "height": 1100705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f321a243cc5ab8de6311aa4335168382951560fa4f810a282e623073bbc4cbf7" } } ], "extra": [ 1, 81, 76, 158, 178, 41, 244, 99, 76, 66, 154, 183, 4, 192, 134, 174, 2, 12, 153, 27, 250, 17, 199, 178, 153, 138, 67, 3, 90, 180, 230, 3, 77, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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