Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 103b6c5073bb83ecec868e86be73873ed84e000f22887cfb34ea14b56cdfd8cb

Tx prefix hash: 88812e78a6ba1d5f9c65dc0257b4e282efc6b55b016d0eeab9e9ffdd5071f02f
Tx public key: 7d86b70525124db6ad423012f2a223e48ab0e37172524f319d2eef605c49f1a1
Timestamp: 1722543406 Timestamp [UCT]: 2024-08-01 20:16:46 Age [y:d:h:m:s]: 00:242:00:35:30
Block: 1078634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172875 RingCT/type: yes/0
Extra: 017d86b70525124db6ad423012f2a223e48ab0e37172524f319d2eef605c49f1a1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95e1f6f03f486c94218d50c77bcaf044bfe505ed989b7a67c38dfd85997c3bf7 0.600000000000 1551247 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": 1078644, "vin": [ { "gen": { "height": 1078634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95e1f6f03f486c94218d50c77bcaf044bfe505ed989b7a67c38dfd85997c3bf7" } } ], "extra": [ 1, 125, 134, 183, 5, 37, 18, 77, 182, 173, 66, 48, 18, 242, 162, 35, 228, 138, 176, 227, 113, 114, 82, 79, 49, 157, 46, 239, 96, 92, 73, 241, 161, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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