Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c51bc8b1acac2c9476efd224c375422fde2c992d161f78038d21b04c50dacc9

Tx prefix hash: 196604dbb1b990ef79e98df93e1bd6b98909ec6423f05d2c907aa472dc9410ed
Tx public key: 428c47fc05993f228a63f258d1a7f1c2da74e5a9d9325a3a8c2a7250323d4f34
Timestamp: 1699198128 Timestamp [UCT]: 2023-11-05 15:28:48 Age [y:d:h:m:s]: 00:361:09:50:31
Block: 885101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258802 RingCT/type: yes/0
Extra: 01428c47fc05993f228a63f258d1a7f1c2da74e5a9d9325a3a8c2a7250323d4f34021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.716626674000 dcy

stealth address amount amount idx
00: 5d4381994049c2ebf53cd4633b7bb467e364a32365a5ca248c39e9523eb56c5c 0.716626674000 1340854 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": 885111, "vin": [ { "gen": { "height": 885101 } } ], "vout": [ { "amount": 716626674, "target": { "key": "5d4381994049c2ebf53cd4633b7bb467e364a32365a5ca248c39e9523eb56c5c" } } ], "extra": [ 1, 66, 140, 71, 252, 5, 153, 63, 34, 138, 99, 242, 88, 209, 167, 241, 194, 218, 116, 229, 169, 217, 50, 90, 58, 140, 42, 114, 80, 50, 61, 79, 52, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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