Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56d4828bfe12b2e3e06c09eaf46ec46cf1fbcb6845d43d3fb7d88de029538b64

Tx prefix hash: 18bd26e5d17dc0ddbb0052c39205f13a37b4a618ca2ee662ddc23e7dd75e0b7c
Tx public key: 2f5c92d021c1273f72faa3bf9f710037f97d500fe480930ef0f4a0f112125f53
Timestamp: 1734709857 Timestamp [UCT]: 2024-12-20 15:50:57 Age [y:d:h:m:s]: 00:117:02:15:49
Block: 1179413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83454 RingCT/type: yes/0
Extra: 012f5c92d021c1273f72faa3bf9f710037f97d500fe480930ef0f4a0f112125f530211000000131f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3617a32f6fa46a13f43877264a01e7e8e245a6845ca449c786b62ba6ddf7c823 0.600000000000 1665808 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": 1179423, "vin": [ { "gen": { "height": 1179413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3617a32f6fa46a13f43877264a01e7e8e245a6845ca449c786b62ba6ddf7c823" } } ], "extra": [ 1, 47, 92, 146, 208, 33, 193, 39, 63, 114, 250, 163, 191, 159, 113, 0, 55, 249, 125, 80, 15, 228, 128, 147, 14, 240, 244, 160, 241, 18, 18, 95, 83, 2, 17, 0, 0, 0, 19, 31, 10, 83, 235, 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