Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a27b750c1ac71145c7afc4c4c0d7b7b37bd10232e50faec6949a5907194fba71

Tx prefix hash: 675e241b27b4e39716e4f8e051646beddbbe593c32505094a2f2375d290532e6
Tx public key: c3c1a3789824cc9943088cdb6f90d7db9cccb949494b213e903c4347c5814c35
Timestamp: 1722716578 Timestamp [UCT]: 2024-08-03 20:22:58 Age [y:d:h:m:s]: 00:247:22:04:38
Block: 1080070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177085 RingCT/type: yes/0
Extra: 01c3c1a3789824cc9943088cdb6f90d7db9cccb949494b213e903c4347c5814c35021100000004e914dd15000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: 9047ac598e9acb7e2417e2879303f806f35463f43a34eba1c9223b96abe90217 0.615610000000 1553287 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": 1080080, "vin": [ { "gen": { "height": 1080070 } } ], "vout": [ { "amount": 615610000, "target": { "key": "9047ac598e9acb7e2417e2879303f806f35463f43a34eba1c9223b96abe90217" } } ], "extra": [ 1, 195, 193, 163, 120, 152, 36, 204, 153, 67, 8, 140, 219, 111, 144, 215, 219, 156, 204, 185, 73, 73, 75, 33, 62, 144, 60, 67, 71, 197, 129, 76, 53, 2, 17, 0, 0, 0, 4, 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