Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da2907e90f40836da7d0b2165c95d54bae0c58e6d419643fc7e70900ccfc9a88

Tx prefix hash: 26b314c508c6a6ba20355e06f1e680cdcd4009f148174afe848df06274525823
Tx public key: a6d191a2d1efd4914f2b091de371a0e4e55ff003bf49f73d9c4ed138cb848112
Timestamp: 1704033030 Timestamp [UCT]: 2023-12-31 14:30:30 Age [y:d:h:m:s]: 01:130:11:19:56
Block: 925172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354386 RingCT/type: yes/0
Extra: 01a6d191a2d1efd4914f2b091de371a0e4e55ff003bf49f73d9c4ed138cb8481120211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42d2aff6569d2639fc7c39d23cc6a231a1648cd069f1daa9618d9e7ffc1bfbde 0.600000000000 1382932 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": 925182, "vin": [ { "gen": { "height": 925172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42d2aff6569d2639fc7c39d23cc6a231a1648cd069f1daa9618d9e7ffc1bfbde" } } ], "extra": [ 1, 166, 209, 145, 162, 209, 239, 212, 145, 79, 43, 9, 29, 227, 113, 160, 228, 229, 95, 240, 3, 191, 73, 247, 61, 156, 78, 209, 56, 203, 132, 129, 18, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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