Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a8d0d10b61c535601b64c0043d018a45e313180802ec9e3a4188eb4d66c1e5

Tx prefix hash: e58a685f507a2ba046b2eea220a0939c4b0dfe6a34ae18570cff49459f780569
Tx public key: 27dae5f83fd6d20de4d90ef9eb628ac835d516de22fdf6896dd159d9f69448d4
Timestamp: 1727834460 Timestamp [UCT]: 2024-10-02 02:01:00 Age [y:d:h:m:s]: 00:193:04:03:02
Block: 1122514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137852 RingCT/type: yes/0
Extra: 0127dae5f83fd6d20de4d90ef9eb628ac835d516de22fdf6896dd159d9f69448d402110000000891e13c04000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: ba4afdba22a3758c335e76234f63fef85f4fda22403f09f2893006f1f3694e19 0.600200000000 1604965 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": 1122524, "vin": [ { "gen": { "height": 1122514 } } ], "vout": [ { "amount": 600200000, "target": { "key": "ba4afdba22a3758c335e76234f63fef85f4fda22403f09f2893006f1f3694e19" } } ], "extra": [ 1, 39, 218, 229, 248, 63, 214, 210, 13, 228, 217, 14, 249, 235, 98, 138, 200, 53, 213, 22, 222, 34, 253, 246, 137, 109, 209, 89, 217, 246, 148, 72, 212, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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