Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9944646b72bad9649e10cf9d6f956811cf6939f4b7d252260d8765df8fbbc2b7

Tx prefix hash: 6cd0a874263ec44cf39084e908d6f1aca41f131254756548d59f855e0ac7cd2b
Tx public key: 6cfcf80ce7e50ff6cdc1a50a5e019cf0df28159f1942538ab204fdfb11a59e54
Timestamp: 1630778973 Timestamp [UCT]: 2021-09-04 18:09:33 Age [y:d:h:m:s]: 03:251:09:45:27
Block: 327445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 954317 RingCT/type: yes/0
Extra: 016cfcf80ce7e50ff6cdc1a50a5e019cf0df28159f1942538ab204fdfb11a59e54021100000034cd14b6bf000000000000000000

1 output(s) for total of 50.471559332000 dcy

stealth address amount amount idx
00: f8803bf35ca84b8983e229b9c95a4e416869542f1b1b039ceb6ae6f30c5318ee 50.471559332000 678124 of 0

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": 327455, "vin": [ { "gen": { "height": 327445 } } ], "vout": [ { "amount": 50471559332, "target": { "key": "f8803bf35ca84b8983e229b9c95a4e416869542f1b1b039ceb6ae6f30c5318ee" } } ], "extra": [ 1, 108, 252, 248, 12, 231, 229, 15, 246, 205, 193, 165, 10, 94, 1, 156, 240, 223, 40, 21, 159, 25, 66, 83, 138, 178, 4, 253, 251, 17, 165, 158, 84, 2, 17, 0, 0, 0, 52, 205, 20, 182, 191, 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