Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7cd30a17cc0d2b8148e7f36b59648bcfe9aaf62087342a005b31664820ee1a2

Tx prefix hash: 575930a2dd9978ecb682c018f44d9db5d2627c2d90aebe77187064c9e61c0c8b
Tx public key: 27a79fdd6d9c3a798cbb6d476c3eb324468e594bfd6e2f0923d9d40e33b2a6e5
Timestamp: 1702511821 Timestamp [UCT]: 2023-12-13 23:57:01 Age [y:d:h:m:s]: 01:184:05:40:43
Block: 912568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392761 RingCT/type: yes/0
Extra: 0127a79fdd6d9c3a798cbb6d476c3eb324468e594bfd6e2f0923d9d40e33b2a6e5021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dc5264529f34d7cb3ff16d4aaa425b7d1a5a0f55a3d739e086ccecdaad441f7 0.600000000000 1369796 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": 912578, "vin": [ { "gen": { "height": 912568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dc5264529f34d7cb3ff16d4aaa425b7d1a5a0f55a3d739e086ccecdaad441f7" } } ], "extra": [ 1, 39, 167, 159, 221, 109, 156, 58, 121, 140, 187, 109, 71, 108, 62, 179, 36, 70, 142, 89, 75, 253, 110, 47, 9, 35, 217, 212, 14, 51, 178, 166, 229, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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