Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c59981509db7d506184d2b1722f740986f32f0fe12b68a600fed5353e5b8b8c1

Tx prefix hash: 7304520959c9304bf8dc84c07add7badc99cb54f7d40f4324fe3c9010e62d219
Tx public key: 82e55aae601cd2570ad4d2db86c1821e58341ebfc5b7cac6b617235bcf69c1a5
Timestamp: 1735921763 Timestamp [UCT]: 2025-01-03 16:29:23 Age [y:d:h:m:s]: 00:347:08:30:06
Block: 1189433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245795 RingCT/type: yes/0
Extra: 0182e55aae601cd2570ad4d2db86c1821e58341ebfc5b7cac6b617235bcf69c1a502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9ecd5129be80254792eccc0f2a17bcad0535adfd2514bfb55c79fa0d6344d43 0.600000000000 1675942 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": 1189443, "vin": [ { "gen": { "height": 1189433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9ecd5129be80254792eccc0f2a17bcad0535adfd2514bfb55c79fa0d6344d43" } } ], "extra": [ 1, 130, 229, 90, 174, 96, 28, 210, 87, 10, 212, 210, 219, 134, 193, 130, 30, 88, 52, 30, 191, 197, 183, 202, 198, 182, 23, 35, 91, 207, 105, 193, 165, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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