Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2985e1dde55299c9c1383f4aee9a6a4295b690619066d16761866e02f4e74c

Tx prefix hash: aa3749c61505eba1cd9fc949410df3e4ea83d856c6f88256018f8111958cb2b2
Tx public key: a1ce96a9fb7835b460661bdc7691c966594377a70d219bd6695acb5adc6e54f0
Timestamp: 1704741061 Timestamp [UCT]: 2024-01-08 19:11:01 Age [y:d:h:m:s]: 01:116:20:52:41
Block: 931041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344649 RingCT/type: yes/0
Extra: 01a1ce96a9fb7835b460661bdc7691c966594377a70d219bd6695acb5adc6e54f00211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e1ccc61ba9fe49e8ed13f57bf53d86cd5a1cbd237ec1d938480d4fcd22e8334 0.600000000000 1388933 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": 931051, "vin": [ { "gen": { "height": 931041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e1ccc61ba9fe49e8ed13f57bf53d86cd5a1cbd237ec1d938480d4fcd22e8334" } } ], "extra": [ 1, 161, 206, 150, 169, 251, 120, 53, 180, 96, 102, 27, 220, 118, 145, 201, 102, 89, 67, 119, 167, 13, 33, 155, 214, 105, 90, 203, 90, 220, 110, 84, 240, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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