Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d18e594539453f9d4a95b6354376fa6386c5747e05ef859240b59763fe7d4f90

Tx prefix hash: ca9dcb8fc6b2745cc4adf00489e3e8be868b973238b0f92312fb7b3d2ddf0979
Tx public key: 6d1740b1bedf9aa6d1a74b2d164d618df72c525c6329c76d71a4783cbae35ef0
Timestamp: 1632362065 Timestamp [UCT]: 2021-09-23 01:54:25 Age [y:d:h:m:s]: 04:050:03:17:11
Block: 339144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1070424 RingCT/type: yes/0
Extra: 016d1740b1bedf9aa6d1a74b2d164d618df72c525c6329c76d71a4783cbae35ef002110000002d8d0de867000000000000000000

1 output(s) for total of 46.161039064000 dcy

stealth address amount amount idx
00: 0c1c84820a63e7b327160739d77eceb5ac004e6bf5e7b86772e8b48f8696272d 46.161039064000 697645 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": 339154, "vin": [ { "gen": { "height": 339144 } } ], "vout": [ { "amount": 46161039064, "target": { "key": "0c1c84820a63e7b327160739d77eceb5ac004e6bf5e7b86772e8b48f8696272d" } } ], "extra": [ 1, 109, 23, 64, 177, 190, 223, 154, 166, 209, 167, 75, 45, 22, 77, 97, 141, 247, 44, 82, 92, 99, 41, 199, 109, 113, 164, 120, 60, 186, 227, 94, 240, 2, 17, 0, 0, 0, 45, 141, 13, 232, 103, 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