Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb556015fe62d73e4a99af1f7c71ca815010e6bb646c42075092962c5ae6da98

Tx prefix hash: 47be1d0cb9d16674f3da7bd8b20b4052f65a8961f58a1e18213f36b7bdddad7e
Tx public key: d7cb47b3fc3cf89bc0bc91991a37e20a8a9ac58cdb1a7ca175f1e8324d941f4c
Timestamp: 1704689660 Timestamp [UCT]: 2024-01-08 04:54:20 Age [y:d:h:m:s]: 01:080:23:52:35
Block: 930601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319001 RingCT/type: yes/0
Extra: 01d7cb47b3fc3cf89bc0bc91991a37e20a8a9ac58cdb1a7ca175f1e8324d941f4c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f4cd9c7e068365fae074260c1eebab244b423f7a803f31fa1779d63104d8c8d 0.600000000000 1388485 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": 930611, "vin": [ { "gen": { "height": 930601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f4cd9c7e068365fae074260c1eebab244b423f7a803f31fa1779d63104d8c8d" } } ], "extra": [ 1, 215, 203, 71, 179, 252, 60, 248, 155, 192, 188, 145, 153, 26, 55, 226, 10, 138, 154, 197, 140, 219, 26, 124, 161, 117, 241, 232, 50, 77, 148, 31, 76, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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