Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c661efa49a6784db4a334d1aae936870857b9b0fcb2b2607f2f758a78c4cb86

Tx prefix hash: 4f1887dae28896ef86bd7fb11a317fec14a3f8cd9a0e9bcc833291937618a608
Tx public key: 5498d5ea6973845d33401bed36e85c1c22432d3d9660a9f51edd41dad57f10f5
Timestamp: 1713246399 Timestamp [UCT]: 2024-04-16 05:46:39 Age [y:d:h:m:s]: 01:205:16:04:22
Block: 1001545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405668 RingCT/type: yes/0
Extra: 015498d5ea6973845d33401bed36e85c1c22432d3d9660a9f51edd41dad57f10f50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb27e05be58e18c0c1121636a936c36952ace50f6c926c3bc0ff1090da5fab1e 0.600000000000 1462051 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": 1001555, "vin": [ { "gen": { "height": 1001545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb27e05be58e18c0c1121636a936c36952ace50f6c926c3bc0ff1090da5fab1e" } } ], "extra": [ 1, 84, 152, 213, 234, 105, 115, 132, 93, 51, 64, 27, 237, 54, 232, 92, 28, 34, 67, 45, 61, 150, 96, 169, 245, 30, 221, 65, 218, 213, 127, 16, 245, 2, 17, 0, 0, 0, 2, 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