Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05cb03cc2c6216325dc76b055f887765f5bb48c79a6acc8aead7e2c3415bc28f

Tx prefix hash: bc39d71e90dbacb1fe594b68d83a1f78b765e2e3a65acb557ebc0684c8e7b8a5
Tx public key: 101c1fd18579e6b64c5878e9c76d98b3bccee2577be78d108f8b6e1870cfdd8a
Timestamp: 1577574973 Timestamp [UCT]: 2019-12-28 23:16:13 Age [y:d:h:m:s]: 05:005:06:09:28
Block: 33902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153751 RingCT/type: yes/0
Extra: 01101c1fd18579e6b64c5878e9c76d98b3bccee2577be78d108f8b6e1870cfdd8a021100000004d81c26c0000000000000000000

1 output(s) for total of 473.897535599000 dcy

stealth address amount amount idx
00: 73d4f6957a3e5dd2ddad93816cdb8b3061c9434a2bfdc45cc91d64d6de43f811 473.897535599000 56938 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": 33912, "vin": [ { "gen": { "height": 33902 } } ], "vout": [ { "amount": 473897535599, "target": { "key": "73d4f6957a3e5dd2ddad93816cdb8b3061c9434a2bfdc45cc91d64d6de43f811" } } ], "extra": [ 1, 16, 28, 31, 209, 133, 121, 230, 182, 76, 88, 120, 233, 199, 109, 152, 179, 188, 206, 226, 87, 123, 231, 141, 16, 143, 139, 110, 24, 112, 207, 221, 138, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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