Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21b4ec005e60f7bc25b4c57dc67c0d3fe3eaf703642a380b85a1d42b75a4799e

Tx prefix hash: 9355db2fbca419f2aa7cb81c8d3522f4d8ef629570642f33c1b305237bc1ef49
Tx public key: 41dcdeba8decfba61c64a71e7bb5d8f898ba3d68df2523bc04cc7109791fa4c7
Timestamp: 1713973826 Timestamp [UCT]: 2024-04-24 15:50:26 Age [y:d:h:m:s]: 00:150:01:04:19
Block: 1007594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107472 RingCT/type: yes/0
Extra: 0141dcdeba8decfba61c64a71e7bb5d8f898ba3d68df2523bc04cc7109791fa4c702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c681950ba7efec4aca0301e9899fb055ba45d5f3a554de460c9a38e65814a8b7 0.600000000000 1468986 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": 1007604, "vin": [ { "gen": { "height": 1007594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c681950ba7efec4aca0301e9899fb055ba45d5f3a554de460c9a38e65814a8b7" } } ], "extra": [ 1, 65, 220, 222, 186, 141, 236, 251, 166, 28, 100, 167, 30, 123, 181, 216, 248, 152, 186, 61, 104, 223, 37, 35, 188, 4, 204, 113, 9, 121, 31, 164, 199, 2, 17, 0, 0, 0, 1, 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