Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c184521896a3e00b5baa41b3583a43e8b16148ff72ea74253ecbafc26fc4b0f8

Tx prefix hash: 9cf66c2376c467c63ffd5847c2ffd6d3072e920c0181ec576be617a91788857e
Tx public key: 77482a1a535cef1b43b61ed9b1c01c9d1cc2236b682cbbe64ee8a3bd509013e9
Timestamp: 1702632112 Timestamp [UCT]: 2023-12-15 09:21:52 Age [y:d:h:m:s]: 02:003:13:21:55
Block: 913562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522313 RingCT/type: yes/0
Extra: 0177482a1a535cef1b43b61ed9b1c01c9d1cc2236b682cbbe64ee8a3bd509013e902110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63bb528073ce0f3f4a94e9ed168e912b3ce99cc2357ca14223a0d4ba894810f5 0.600000000000 1370836 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": 913572, "vin": [ { "gen": { "height": 913562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63bb528073ce0f3f4a94e9ed168e912b3ce99cc2357ca14223a0d4ba894810f5" } } ], "extra": [ 1, 119, 72, 42, 26, 83, 92, 239, 27, 67, 182, 30, 217, 177, 192, 28, 157, 28, 194, 35, 107, 104, 44, 187, 230, 78, 232, 163, 189, 80, 144, 19, 233, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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