Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cbdf62ab7f0517dab0b5bc6368d6bccc33997bff8f4a71a175b73ced1a153c0

Tx prefix hash: 3ae5b05069bce3b5eab474d2bc3cc0a0482b21b577fc487a370ba0fcf1a4a3d0
Tx public key: 4914cca3350e256e1236b00edf27dde9f8ca7771f88a6e58027091e4328d51d5
Timestamp: 1625629176 Timestamp [UCT]: 2021-07-07 03:39:36 Age [y:d:h:m:s]: 03:193:04:10:39
Block: 289448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 908296 RingCT/type: yes/0
Extra: 014914cca3350e256e1236b00edf27dde9f8ca7771f88a6e58027091e4328d51d5021100000015694a138f000000000000000000

1 output(s) for total of 67.443348795000 dcy

stealth address amount amount idx
00: 7c58644d2a35efa875d2901ffb34b4485c20fb66432b36c5d3e782e97bc63d6b 67.443348795000 606222 of 0

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": 289458, "vin": [ { "gen": { "height": 289448 } } ], "vout": [ { "amount": 67443348795, "target": { "key": "7c58644d2a35efa875d2901ffb34b4485c20fb66432b36c5d3e782e97bc63d6b" } } ], "extra": [ 1, 73, 20, 204, 163, 53, 14, 37, 110, 18, 54, 176, 14, 223, 39, 221, 233, 248, 202, 119, 113, 248, 138, 110, 88, 2, 112, 145, 228, 50, 141, 81, 213, 2, 17, 0, 0, 0, 21, 105, 74, 19, 143, 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