Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75eb891e48ca8ac1a6d2da2d7730f996ca2b76ad056a0143d5fdb8de04328abe

Tx prefix hash: 516201439629de717dec1073d665f6f94f9859647ff13d51248cce4c9c1580c3
Tx public key: a05de9acee803de3e89aca0d2bff4c1054365ca96ed9ab9c2cb6c2f1ef9a19be
Timestamp: 1731045717 Timestamp [UCT]: 2024-11-08 06:01:57 Age [y:d:h:m:s]: 00:015:22:08:36
Block: 1149045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11395 RingCT/type: yes/0
Extra: 01a05de9acee803de3e89aca0d2bff4c1054365ca96ed9ab9c2cb6c2f1ef9a19be021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b2d4ace71bf3ad15e30f64f353b953dc5ebfd398c0acd544f77f89a38a3c55 0.600000000000 1634030 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": 1149055, "vin": [ { "gen": { "height": 1149045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b2d4ace71bf3ad15e30f64f353b953dc5ebfd398c0acd544f77f89a38a3c55" } } ], "extra": [ 1, 160, 93, 233, 172, 238, 128, 61, 227, 232, 154, 202, 13, 43, 255, 76, 16, 84, 54, 92, 169, 110, 217, 171, 156, 44, 182, 194, 241, 239, 154, 25, 190, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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