Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e74e79bb4edf4d942d47f1c9ef8d6731ffcd41cca80c010e07d1728580d8ddf

Tx prefix hash: 877e7819ceffc9b1f1c99e6242c76b715bf59bd2a5e84c1296a6b0f97d9d01c4
Tx public key: b6be0c826fdd5f58a7d0b5404c54fccd197f444aa332d2bbb6653a8ab78ed237
Timestamp: 1697369812 Timestamp [UCT]: 2023-10-15 11:36:52 Age [y:d:h:m:s]: 01:174:10:06:19
Block: 870147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385667 RingCT/type: yes/0
Extra: 01b6be0c826fdd5f58a7d0b5404c54fccd197f444aa332d2bbb6653a8ab78ed237021100000005faf35c9c000000000000000000

1 output(s) for total of 0.803233478000 dcy

stealth address amount amount idx
00: acdc4b724dc784d280375ae64aee75a4264af10396cae4940682c3aa95d43d62 0.803233478000 1325020 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": 870157, "vin": [ { "gen": { "height": 870147 } } ], "vout": [ { "amount": 803233478, "target": { "key": "acdc4b724dc784d280375ae64aee75a4264af10396cae4940682c3aa95d43d62" } } ], "extra": [ 1, 182, 190, 12, 130, 111, 221, 95, 88, 167, 208, 181, 64, 76, 84, 252, 205, 25, 127, 68, 74, 163, 50, 210, 187, 182, 101, 58, 138, 183, 142, 210, 55, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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