Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfb0286e096c8ba18b8ae50fbc0edfbb44a9cc3239baced49a6e40f2647e0d7a

Tx prefix hash: 3d26b788d2c1088647a650a5fee2831d0679e4ce01555e270bd255f552acb449
Tx public key: bbbd4b0ec3d4b21d42b78dc9eea36621cdf6243ea3fdd7ca386acc47c8598b45
Timestamp: 1735265043 Timestamp [UCT]: 2024-12-27 02:04:03 Age [y:d:h:m:s]: 00:096:19:48:47
Block: 1183981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68983 RingCT/type: yes/0
Extra: 01bbbd4b0ec3d4b21d42b78dc9eea36621cdf6243ea3fdd7ca386acc47c8598b45021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fd17c221dc4354765efb890514e1379699a995e80cb2072bb927e7d64899fed 0.600000000000 1670432 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": 1183991, "vin": [ { "gen": { "height": 1183981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fd17c221dc4354765efb890514e1379699a995e80cb2072bb927e7d64899fed" } } ], "extra": [ 1, 187, 189, 75, 14, 195, 212, 178, 29, 66, 183, 141, 201, 238, 163, 102, 33, 205, 246, 36, 62, 163, 253, 215, 202, 56, 106, 204, 71, 200, 89, 139, 69, 2, 17, 0, 0, 0, 5, 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