Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b3c41bf30d41cfab1ee13634b023ac775be7a0f42b234db0c975690ea6199d5

Tx prefix hash: 041a322ccf8343f44eef57879d4abc3bc6c2a7a28d1c3b351a0b2e21d55773b0
Tx public key: 6d4dafdc8828a2e9a9b4c21551e42133b5bb136c2e186fd9951a32939b2ed966
Timestamp: 1725601656 Timestamp [UCT]: 2024-09-06 05:47:36 Age [y:d:h:m:s]: 00:284:11:03:14
Block: 1103998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203075 RingCT/type: yes/0
Extra: 016d4dafdc8828a2e9a9b4c21551e42133b5bb136c2e186fd9951a32939b2ed966021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 335cb215c407c5af6d00e77cc6830644e32d307a6369dc9762475aeb29378df3 0.600000000000 1581045 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": 1104008, "vin": [ { "gen": { "height": 1103998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "335cb215c407c5af6d00e77cc6830644e32d307a6369dc9762475aeb29378df3" } } ], "extra": [ 1, 109, 77, 175, 220, 136, 40, 162, 233, 169, 180, 194, 21, 81, 228, 33, 51, 181, 187, 19, 108, 46, 24, 111, 217, 149, 26, 50, 147, 155, 46, 217, 102, 2, 17, 0, 0, 0, 4, 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