Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 273d7de26cd36972b1a73b5c71cb8c214be71260fdd6abb03b77ff17c1c5d562

Tx prefix hash: 3b37ce17db6e0c07115a6219fe784b71e5213874264a3ceea93eee218b94c09b
Tx public key: f633bf55ac1a3d7d79c2fafcaf374314b896ad6885b862a649ad8615204da421
Timestamp: 1696004844 Timestamp [UCT]: 2023-09-29 16:27:24 Age [y:d:h:m:s]: 01:149:00:27:37
Block: 858827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367523 RingCT/type: yes/0
Extra: 01f633bf55ac1a3d7d79c2fafcaf374314b896ad6885b862a649ad8615204da42102110000000be6d27f9c000000000000000000

1 output(s) for total of 0.875688561000 dcy

stealth address amount amount idx
00: 23c6ed456dbe29a426397e4cdd0f0c191d7dc63ad99feca1e1b1b0d69f6af154 0.875688561000 1313023 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": 858837, "vin": [ { "gen": { "height": 858827 } } ], "vout": [ { "amount": 875688561, "target": { "key": "23c6ed456dbe29a426397e4cdd0f0c191d7dc63ad99feca1e1b1b0d69f6af154" } } ], "extra": [ 1, 246, 51, 191, 85, 172, 26, 61, 125, 121, 194, 250, 252, 175, 55, 67, 20, 184, 150, 173, 104, 133, 184, 98, 166, 73, 173, 134, 21, 32, 77, 164, 33, 2, 17, 0, 0, 0, 11, 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