Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747f482870d76b077ccb69a7b24ad73276bfa51fea23fa463aebc7a7fac2f4c6

Tx prefix hash: cee4c36475df4a1ee130e37903c8446c79d87391dec8156e8fe43b3640636789
Tx public key: 822c41774ea159e8cea8c2971d00c74252b2dbda1fdb0a5f21684a574ac231c5
Timestamp: 1632826872 Timestamp [UCT]: 2021-09-28 11:01:12 Age [y:d:h:m:s]: 03:096:01:38:46
Block: 342459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 845417 RingCT/type: yes/0
Extra: 01822c41774ea159e8cea8c2971d00c74252b2dbda1fdb0a5f21684a574ac231c5021100000037f60c5d7e000000000000000000

1 output(s) for total of 45.016465642000 dcy

stealth address amount amount idx
00: fc6101dd1af90bb265e15eade88dc03bf3c21d9ff77d553b135dc0838a030ac2 45.016465642000 703237 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": 342469, "vin": [ { "gen": { "height": 342459 } } ], "vout": [ { "amount": 45016465642, "target": { "key": "fc6101dd1af90bb265e15eade88dc03bf3c21d9ff77d553b135dc0838a030ac2" } } ], "extra": [ 1, 130, 44, 65, 119, 78, 161, 89, 232, 206, 168, 194, 151, 29, 0, 199, 66, 82, 178, 219, 218, 31, 219, 10, 95, 33, 104, 74, 87, 74, 194, 49, 197, 2, 17, 0, 0, 0, 55, 246, 12, 93, 126, 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