Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a314ed744b302921de7b2b575bf8c8b7bbd8b70ed158112e7aff31d471573c82

Tx prefix hash: 9d06526ff005faa8434c3fe2f4b5d7d174d6622efcb22ac773bd3f51234d8f22
Tx public key: a87f2e8ac7061b41f0c602d0224e8f5d109ac5a9e832668bb1dbeda35735b4be
Timestamp: 1673823676 Timestamp [UCT]: 2023-01-15 23:01:16 Age [y:d:h:m:s]: 02:091:21:30:34
Block: 675589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587356 RingCT/type: yes/0
Extra: 01a87f2e8ac7061b41f0c602d0224e8f5d109ac5a9e832668bb1dbeda35735b4be0211000000078b7b6602000000000000000000

1 output(s) for total of 3.543995336000 dcy

stealth address amount amount idx
00: 4a057a0c04a359c0273d8350306e704cf289a4018105ed26c61fe822bc21934a 3.543995336000 1117268 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": 675599, "vin": [ { "gen": { "height": 675589 } } ], "vout": [ { "amount": 3543995336, "target": { "key": "4a057a0c04a359c0273d8350306e704cf289a4018105ed26c61fe822bc21934a" } } ], "extra": [ 1, 168, 127, 46, 138, 199, 6, 27, 65, 240, 198, 2, 208, 34, 78, 143, 93, 16, 154, 197, 169, 232, 50, 102, 139, 177, 219, 237, 163, 87, 53, 180, 190, 2, 17, 0, 0, 0, 7, 139, 123, 102, 2, 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