Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbbd4558e613068984d4dbd9b51a0c1e8f4e596f876cef58622c15ee64afc18f

Tx prefix hash: f2144e1fa9318390422089ef09093247d7cf4e371ecaf0635681a43603fa204d
Tx public key: 3d959def3cf2003e8f0aadb2434d534e7f314a7c40ff278a60c6b6057bd13359
Timestamp: 1699688139 Timestamp [UCT]: 2023-11-11 07:35:39 Age [y:d:h:m:s]: 01:139:10:06:12
Block: 889169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360820 RingCT/type: yes/0
Extra: 013d959def3cf2003e8f0aadb2434d534e7f314a7c40ff278a60c6b6057bd13359021100000003faf35c9c000000000000000000

1 output(s) for total of 0.694726701000 dcy

stealth address amount amount idx
00: 0d1d912a6150921c07fb4464157a0fc4557012c55853afa34db7a50fa548fb80 0.694726701000 1345146 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": 889179, "vin": [ { "gen": { "height": 889169 } } ], "vout": [ { "amount": 694726701, "target": { "key": "0d1d912a6150921c07fb4464157a0fc4557012c55853afa34db7a50fa548fb80" } } ], "extra": [ 1, 61, 149, 157, 239, 60, 242, 0, 62, 143, 10, 173, 178, 67, 77, 83, 78, 127, 49, 74, 124, 64, 255, 39, 138, 96, 198, 182, 5, 123, 209, 51, 89, 2, 17, 0, 0, 0, 3, 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