Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa4a4be3815ff6b248d085b393703fdd6b1dd9af97a4ba767f25aeed1d8a0d45

Tx prefix hash: 9dfeaa34097b303e2e31773abe46e2315b2a3c05f3e68869f6146d7a15674760
Tx public key: 7ac8aeab0cf6048aa8f92fd21dfa58e59e713d8dc43b43314142946775baca72
Timestamp: 1675205151 Timestamp [UCT]: 2023-01-31 22:45:51 Age [y:d:h:m:s]: 02:103:23:52:50
Block: 687054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595995 RingCT/type: yes/0
Extra: 017ac8aeab0cf6048aa8f92fd21dfa58e59e713d8dc43b43314142946775baca720211000000035029cbac000000000000000000

1 output(s) for total of 3.247168464000 dcy

stealth address amount amount idx
00: 353b34bebee8e83cb8c89356f6dd93eef02e327aa1f1b22106f1195ff81cbd84 3.247168464000 1129606 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": 687064, "vin": [ { "gen": { "height": 687054 } } ], "vout": [ { "amount": 3247168464, "target": { "key": "353b34bebee8e83cb8c89356f6dd93eef02e327aa1f1b22106f1195ff81cbd84" } } ], "extra": [ 1, 122, 200, 174, 171, 12, 246, 4, 138, 168, 249, 47, 210, 29, 250, 88, 229, 158, 113, 61, 141, 196, 59, 67, 49, 65, 66, 148, 103, 117, 186, 202, 114, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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