Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7353556993a24c54e15f96042af38b9fc1cb90651bbf28881b7ba7cad83480e6

Tx prefix hash: 631889e75f8c4bf55aeb0fcf7ffca04805775bd91e3585a42d18206379b37eab
Tx public key: f3152af87ed6fdf7436f1b584df1b6f02041a163aeeb512f958fb31378101f4d
Timestamp: 1705858210 Timestamp [UCT]: 2024-01-21 17:30:10 Age [y:d:h:m:s]: 00:356:02:33:09
Block: 940286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254955 RingCT/type: yes/0
Extra: 01f3152af87ed6fdf7436f1b584df1b6f02041a163aeeb512f958fb31378101f4d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0e18e582c2c1a0f4a038a9ae3bad10d96d4d3ef540a673b45abab54f54c1373 0.600000000000 1398422 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": 940296, "vin": [ { "gen": { "height": 940286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0e18e582c2c1a0f4a038a9ae3bad10d96d4d3ef540a673b45abab54f54c1373" } } ], "extra": [ 1, 243, 21, 42, 248, 126, 214, 253, 247, 67, 111, 27, 88, 77, 241, 182, 240, 32, 65, 161, 99, 174, 235, 81, 47, 149, 143, 179, 19, 120, 16, 31, 77, 2, 17, 0, 0, 0, 4, 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