Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fc87833d2d64702d3f0d4b64b3d5a1d09d61456b2f497e795db567e4c870244

Tx prefix hash: 7bc862c2391d79cca43f3b943f5f99599a13061e19439ec3df42b3075c973e32
Tx public key: c58a269e0f9f1fa90f4929e21840248bff372e3a4c0a70850453c92b4a020de3
Timestamp: 1731168737 Timestamp [UCT]: 2024-11-09 16:12:17 Age [y:d:h:m:s]: 00:131:02:44:08
Block: 1150069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93535 RingCT/type: yes/0
Extra: 01c58a269e0f9f1fa90f4929e21840248bff372e3a4c0a70850453c92b4a020de3021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b940b053ca4a1b86e4457ddca4310e301a1baf7d954f50a322708933de199adf 0.600000000000 1635270 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": 1150079, "vin": [ { "gen": { "height": 1150069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b940b053ca4a1b86e4457ddca4310e301a1baf7d954f50a322708933de199adf" } } ], "extra": [ 1, 197, 138, 38, 158, 15, 159, 31, 169, 15, 73, 41, 226, 24, 64, 36, 139, 255, 55, 46, 58, 76, 10, 112, 133, 4, 83, 201, 43, 74, 2, 13, 227, 2, 17, 0, 0, 0, 1, 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