Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c19950f89cc28c2ad3e7acb3265be90e1a95bc8286f1dd49c1867470c5bafec

Tx prefix hash: 04be242ab2d7e51545924fa37a32d78a1dfb20d755f15804e5eceda0a9c181e5
Tx public key: af2bc9599bf903b5159ac4aba08efe07e5301ebdc0fd25d6f9f74201659d14f3
Timestamp: 1715396696 Timestamp [UCT]: 2024-05-11 03:04:56 Age [y:d:h:m:s]: 00:276:13:19:22
Block: 1019418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197635 RingCT/type: yes/0
Extra: 01af2bc9599bf903b5159ac4aba08efe07e5301ebdc0fd25d6f9f74201659d14f302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1301cc87c2b421db2aea941d77e04e16f4c16a6a9153e1aaa78262c20e3eba08 0.600000000000 1483379 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": 1019428, "vin": [ { "gen": { "height": 1019418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1301cc87c2b421db2aea941d77e04e16f4c16a6a9153e1aaa78262c20e3eba08" } } ], "extra": [ 1, 175, 43, 201, 89, 155, 249, 3, 181, 21, 154, 196, 171, 160, 142, 254, 7, 229, 48, 30, 189, 192, 253, 37, 214, 249, 247, 66, 1, 101, 157, 20, 243, 2, 17, 0, 0, 0, 3, 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