Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de5196e7c4c1ecfe281ad85005153294afb4af979a107fcb796abf44a02912e9

Tx prefix hash: 93cbe599ed75e87161e77ed68ed0f7eb42a22d1a624d2f4ef8e53c6f69d9c12e
Tx public key: 74eb2851401b5331e7600ebf0be76c52a93df4f11542c1ba6b741f32d6128bef
Timestamp: 1750092459 Timestamp [UCT]: 2025-06-16 16:47:39 Age [y:d:h:m:s]: 00:157:02:10:41
Block: 1306363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110067 RingCT/type: yes/0
Extra: 0174eb2851401b5331e7600ebf0be76c52a93df4f11542c1ba6b741f32d6128bef0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43c81a26a73f36c488af35cb4f5aa4abd4159db2b924505fd5657af2cfb0baf8 0.600000000000 1793968 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": 1306373, "vin": [ { "gen": { "height": 1306363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43c81a26a73f36c488af35cb4f5aa4abd4159db2b924505fd5657af2cfb0baf8" } } ], "extra": [ 1, 116, 235, 40, 81, 64, 27, 83, 49, 231, 96, 14, 191, 11, 231, 108, 82, 169, 61, 244, 241, 21, 66, 193, 186, 107, 116, 31, 50, 214, 18, 139, 239, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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