Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f28d7cc30c5ace6e1a61c2a2b30e3355f20611dd0dcbdb433d8961f391aade9

Tx prefix hash: 5dac86dc5709c414a0825ed1d23a53851ef37c45b3c485f8ef3a492082489c6b
Tx public key: e31420255a97e7d53d146dff5fc7c19054d0dfc8764265fe784de9f6a2cc227f
Timestamp: 1722886797 Timestamp [UCT]: 2024-08-05 19:39:57 Age [y:d:h:m:s]: 00:238:08:53:57
Block: 1081487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170251 RingCT/type: yes/0
Extra: 01e31420255a97e7d53d146dff5fc7c19054d0dfc8764265fe784de9f6a2cc227f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2eeea7443e65fc5b9b6d116a823d7a6aca18182760d83594adf0c53ca6ffcee0 0.600000000000 1555252 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": 1081497, "vin": [ { "gen": { "height": 1081487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eeea7443e65fc5b9b6d116a823d7a6aca18182760d83594adf0c53ca6ffcee0" } } ], "extra": [ 1, 227, 20, 32, 37, 90, 151, 231, 213, 61, 20, 109, 255, 95, 199, 193, 144, 84, 208, 223, 200, 118, 66, 101, 254, 120, 77, 233, 246, 162, 204, 34, 127, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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