Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf1f6be9648b73e2193d256441d2c98e1b925d57fee12e97f570864fb9702b9

Tx prefix hash: 1bd390c7783be06a7a2dd8ea82a214a726ed38788e0bf180b294afa373419b12
Tx public key: 578530500a68b5a8b16045da36525f9de9bb3a2fe2965c245a5b2ccc2f6fa00a
Timestamp: 1679060556 Timestamp [UCT]: 2023-03-17 13:42:36 Age [y:d:h:m:s]: 01:301:14:27:52
Block: 719040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476450 RingCT/type: yes/0
Extra: 01578530500a68b5a8b16045da36525f9de9bb3a2fe2965c245a5b2ccc2f6fa00a021100000003b3164c24000000000000000000

1 output(s) for total of 2.544027946000 dcy

stealth address amount amount idx
00: 2100952de740ec3be16cd8ea934570034c60d79e1c62ac657e60dbff4dd3e515 2.544027946000 1163741 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": 719050, "vin": [ { "gen": { "height": 719040 } } ], "vout": [ { "amount": 2544027946, "target": { "key": "2100952de740ec3be16cd8ea934570034c60d79e1c62ac657e60dbff4dd3e515" } } ], "extra": [ 1, 87, 133, 48, 80, 10, 104, 181, 168, 177, 96, 69, 218, 54, 82, 95, 157, 233, 187, 58, 47, 226, 150, 92, 36, 90, 91, 44, 204, 47, 111, 160, 10, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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