Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f5d482024e83c9a31de99015d291c6122064ddfdff2c3f4bc6e43125d762e00

Tx prefix hash: d6cf0a43413e854aaede9285d1c09392834a39ac11842a01ec158ec82e0b804f
Tx public key: 4c2b0e836fbe2d7ae223b0f5f6267db8ee46375798e95162a9bf38ba2f7af104
Timestamp: 1674288013 Timestamp [UCT]: 2023-01-21 08:00:13 Age [y:d:h:m:s]: 02:002:11:03:36
Block: 679443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523603 RingCT/type: yes/0
Extra: 014c2b0e836fbe2d7ae223b0f5f6267db8ee46375798e95162a9bf38ba2f7af1040211000000025029cbac000000000000000000

1 output(s) for total of 3.441305544000 dcy

stealth address amount amount idx
00: 4c4fee050bb9a6d60ef9eb44db7799cae9777c6e7c3a524559092f00b0136b8e 3.441305544000 1121420 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": 679453, "vin": [ { "gen": { "height": 679443 } } ], "vout": [ { "amount": 3441305544, "target": { "key": "4c4fee050bb9a6d60ef9eb44db7799cae9777c6e7c3a524559092f00b0136b8e" } } ], "extra": [ 1, 76, 43, 14, 131, 111, 190, 45, 122, 226, 35, 176, 245, 246, 38, 125, 184, 238, 70, 55, 87, 152, 233, 81, 98, 169, 191, 56, 186, 47, 122, 241, 4, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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