Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bfe8e38347917bcfb88e784459e369aa608b9ce75f7cbfd1e3aeda9e676ee7f

Tx prefix hash: 5383fe156f05f78096155d800cdb0e69e7d5eec604772ba8ff7b3cfbae5d04f4
Tx public key: 0e6950c929b2b56073812b16421d8f6a3fa878935bcd5dfb7ebf3ff53db412e6
Timestamp: 1713448773 Timestamp [UCT]: 2024-04-18 13:59:33 Age [y:d:h:m:s]: 00:206:15:45:00
Block: 1003229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147943 RingCT/type: yes/0
Extra: 010e6950c929b2b56073812b16421d8f6a3fa878935bcd5dfb7ebf3ff53db412e602110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce342ac602845309f1e1eb5bde2e7172e76ed4c70a1b36966c84af59358798f6 0.600000000000 1463759 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": 1003239, "vin": [ { "gen": { "height": 1003229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce342ac602845309f1e1eb5bde2e7172e76ed4c70a1b36966c84af59358798f6" } } ], "extra": [ 1, 14, 105, 80, 201, 41, 178, 181, 96, 115, 129, 43, 22, 66, 29, 143, 106, 63, 168, 120, 147, 91, 205, 93, 251, 126, 191, 63, 245, 61, 180, 18, 230, 2, 17, 0, 0, 0, 11, 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