Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d159013d9e3a878b435f0aabad48cf21ddde1b3b9d9a0d4f558e64c9639e20a

Tx prefix hash: 6335a76d2b7e74c447b8700cd73c2acf1247eee9b3a7e14a341396d6f44ac56c
Tx public key: f5e8aaf3b353d18afaf5d4e18651bf3951f6495d7369633ac3f9785b735fe578
Timestamp: 1705833245 Timestamp [UCT]: 2024-01-21 10:34:05 Age [y:d:h:m:s]: 01:337:16:58:23
Block: 940077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500233 RingCT/type: yes/0
Extra: 01f5e8aaf3b353d18afaf5d4e18651bf3951f6495d7369633ac3f9785b735fe5780211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e2e433fd698c0d7abf4a9e4a6056da9389b924a66850d38f756351dbc756ddc 0.600000000000 1398211 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": 940087, "vin": [ { "gen": { "height": 940077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e2e433fd698c0d7abf4a9e4a6056da9389b924a66850d38f756351dbc756ddc" } } ], "extra": [ 1, 245, 232, 170, 243, 179, 83, 209, 138, 250, 245, 212, 225, 134, 81, 191, 57, 81, 246, 73, 93, 115, 105, 99, 58, 195, 249, 120, 91, 115, 95, 229, 120, 2, 17, 0, 0, 0, 6, 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