Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f41deac3c07e0e3efe01dcec86171cb4aaf858ddaa3acd4ee8387177f5269cea

Tx prefix hash: 2edea70606f4a92bf00f413bfa6620076ee9b530c1c959c1c8d783c6c75230ba
Tx public key: 36817c86ea41daffaa163fd0b6a332d449e50d6de02db11ef5d7de4fc32c53e9
Timestamp: 1727151096 Timestamp [UCT]: 2024-09-24 04:11:36 Age [y:d:h:m:s]: 00:230:16:29:23
Block: 1116841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164709 RingCT/type: yes/0
Extra: 0136817c86ea41daffaa163fd0b6a332d449e50d6de02db11ef5d7de4fc32c53e902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b7c9e83bb4a2e476e566c76a5dd83eed872e6e765359c29e75ac0b4f52ce1a7 0.600000000000 1597468 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": 1116851, "vin": [ { "gen": { "height": 1116841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b7c9e83bb4a2e476e566c76a5dd83eed872e6e765359c29e75ac0b4f52ce1a7" } } ], "extra": [ 1, 54, 129, 124, 134, 234, 65, 218, 255, 170, 22, 63, 208, 182, 163, 50, 212, 73, 229, 13, 109, 224, 45, 177, 30, 245, 215, 222, 79, 195, 44, 83, 233, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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