Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b6410bd67e3fcd9f9643b8ee1b3e0e3b30314b65e3bee912d03737201e269ff

Tx prefix hash: ef65f1d5eeadf81f170a9330dd98aa34ee58621eafc888121d4a282b05b7c3e0
Tx public key: 1b5831dd5bcb8e962a79d45de8c590183e81001c6001cb5059b71b5f5b8a5d1a
Timestamp: 1723306039 Timestamp [UCT]: 2024-08-10 16:07:19 Age [y:d:h:m:s]: 00:219:07:57:51
Block: 1084966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156649 RingCT/type: yes/0
Extra: 011b5831dd5bcb8e962a79d45de8c590183e81001c6001cb5059b71b5f5b8a5d1a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82ea4d5754f00f0459d9f7ee31c87996d1de29672e9eb359c9b89a5a39b544c9 0.600000000000 1559427 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": 1084976, "vin": [ { "gen": { "height": 1084966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82ea4d5754f00f0459d9f7ee31c87996d1de29672e9eb359c9b89a5a39b544c9" } } ], "extra": [ 1, 27, 88, 49, 221, 91, 203, 142, 150, 42, 121, 212, 93, 232, 197, 144, 24, 62, 129, 0, 28, 96, 1, 203, 80, 89, 183, 27, 95, 91, 138, 93, 26, 2, 17, 0, 0, 0, 4, 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