Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84ded0fddbcebba362eb15e80d72458daa7cd0d3d417e4bf4e3f9b70eca8c37

Tx prefix hash: 0acc176a9803e4d8adf0cfffa9999778cf3dd89b32f720fa4a39c2a5287424b4
Tx public key: 6be8400f6c9c5944d561dcad77fe57425780a2cc32a6c7266f120768ee19b2df
Timestamp: 1710264460 Timestamp [UCT]: 2024-03-12 17:27:40 Age [y:d:h:m:s]: 00:316:22:02:48
Block: 976851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226810 RingCT/type: yes/0
Extra: 016be8400f6c9c5944d561dcad77fe57425780a2cc32a6c7266f120768ee19b2df02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47b582870a1486831648dff6d7d8c70a92878a4a08c8f35404f904d602ffef3e 0.600000000000 1436850 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": 976861, "vin": [ { "gen": { "height": 976851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47b582870a1486831648dff6d7d8c70a92878a4a08c8f35404f904d602ffef3e" } } ], "extra": [ 1, 107, 232, 64, 15, 108, 156, 89, 68, 213, 97, 220, 173, 119, 254, 87, 66, 87, 128, 162, 204, 50, 166, 199, 38, 111, 18, 7, 104, 238, 25, 178, 223, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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