Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59979556ddaeb0885ae9b7c8f931a403b8ec676c9db2e3f34b5b770b073930a2

Tx prefix hash: d61cef0a2d54582bdfec82a074a79448f3a1153903de703cda7a88312f7af8a1
Tx public key: 3e4e703d42a91a226b16841c43f62a915dde2231631a8cd579fe6f1e139fcc69
Timestamp: 1698509944 Timestamp [UCT]: 2023-10-28 16:19:04 Age [y:d:h:m:s]: 01:198:17:06:44
Block: 879608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403043 RingCT/type: yes/0
Extra: 013e4e703d42a91a226b16841c43f62a915dde2231631a8cd579fe6f1e139fcc6902110000000afaf35c9c000000000000000000

1 output(s) for total of 0.747297564000 dcy

stealth address amount amount idx
00: f46fda2135701467e43e17ab5859428d4c959939d2353070507d0459fabe5a77 0.747297564000 1335142 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": 879618, "vin": [ { "gen": { "height": 879608 } } ], "vout": [ { "amount": 747297564, "target": { "key": "f46fda2135701467e43e17ab5859428d4c959939d2353070507d0459fabe5a77" } } ], "extra": [ 1, 62, 78, 112, 61, 66, 169, 26, 34, 107, 22, 132, 28, 67, 246, 42, 145, 93, 222, 34, 49, 99, 26, 140, 213, 121, 254, 111, 30, 19, 159, 204, 105, 2, 17, 0, 0, 0, 10, 250, 243, 92, 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