Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a82fbb35aa40340b964f080e2cd2dff2cb4eba89024ef64923a2bf318b4a71d5

Tx prefix hash: 519bfea2b312dd9a38784e4794b743df799fe4ab18e2d25b2f8b1fbada450afa
Tx public key: e8c4aeaad46f8d586dfd2429051bc35a6c84a46aa7c591dec71dde668b04d43c
Timestamp: 1718406880 Timestamp [UCT]: 2024-06-14 23:14:40 Age [y:d:h:m:s]: 00:191:13:34:37
Block: 1044353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137122 RingCT/type: yes/0
Extra: 01e8c4aeaad46f8d586dfd2429051bc35a6c84a46aa7c591dec71dde668b04d43c02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98fa1cc95297d1f616ca2419485bfe897cde174309b6c525cb46d96cbd77fbfd 0.600000000000 1513638 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": 1044363, "vin": [ { "gen": { "height": 1044353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98fa1cc95297d1f616ca2419485bfe897cde174309b6c525cb46d96cbd77fbfd" } } ], "extra": [ 1, 232, 196, 174, 170, 212, 111, 141, 88, 109, 253, 36, 41, 5, 27, 195, 90, 108, 132, 164, 106, 167, 197, 145, 222, 199, 29, 222, 102, 139, 4, 212, 60, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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