Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38e4252de9e2b7a37ce84e1b77dc6c0d495115e90cb54c31c41057b10c81517

Tx prefix hash: af59b0ac0ed2ae737adb6606bd9f579ef5256e61d3546f2dd76d6478b4c2657f
Tx public key: 8683b4066b113c9c9dc910998f6bf76f98f181abd454417862eb4e07bd2e834d
Timestamp: 1721720369 Timestamp [UCT]: 2024-07-23 07:39:29 Age [y:d:h:m:s]: 00:254:16:10:09
Block: 1071812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181934 RingCT/type: yes/0
Extra: 018683b4066b113c9c9dc910998f6bf76f98f181abd454417862eb4e07bd2e834d02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a044fd49d26166e7f5e4b4023607290be7730b30e18fec8fc6ca2fc83a5df73 0.600000000000 1544179 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": 1071822, "vin": [ { "gen": { "height": 1071812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a044fd49d26166e7f5e4b4023607290be7730b30e18fec8fc6ca2fc83a5df73" } } ], "extra": [ 1, 134, 131, 180, 6, 107, 17, 60, 156, 157, 201, 16, 153, 143, 107, 247, 111, 152, 241, 129, 171, 212, 84, 65, 120, 98, 235, 78, 7, 189, 46, 131, 77, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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