Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6fce80f3e67c4612374b69ff12dcfa3e8accf2fd7f3e019f9dec5ae708d3145

Tx prefix hash: 498333dfb7883c9dcda69be67e99b7ea0738822b3f9c590556018cb4bc6c23a4
Tx public key: 6e4ebaf59b969f97d5b1e4721a14770226027129296e985767db1329c5eaa6e3
Timestamp: 1730489720 Timestamp [UCT]: 2024-11-01 19:35:20 Age [y:d:h:m:s]: 00:181:20:12:34
Block: 1144425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129822 RingCT/type: yes/0
Extra: 016e4ebaf59b969f97d5b1e4721a14770226027129296e985767db1329c5eaa6e3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 358f4d3842f29e0d27f1f5277af250855c049499e66fca32667066e7317dc7d2 0.600000000000 1628646 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": 1144435, "vin": [ { "gen": { "height": 1144425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "358f4d3842f29e0d27f1f5277af250855c049499e66fca32667066e7317dc7d2" } } ], "extra": [ 1, 110, 78, 186, 245, 155, 150, 159, 151, 213, 177, 228, 114, 26, 20, 119, 2, 38, 2, 113, 41, 41, 110, 152, 87, 103, 219, 19, 41, 197, 234, 166, 227, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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