Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7bedae6e29d368f1dcfe90dc85502f2fafefd678156926e5bacf87a66b7d86c

Tx prefix hash: b511bd6e1b20f41c6737493cda3253f8fbcaa901ab4b5471be6a7ad28f82aacc
Tx public key: 4285b1ea165c5a24ba1d47518361647c1a8cd59a4e432e014c0d2d1169703f8b
Timestamp: 1700819604 Timestamp [UCT]: 2023-11-24 09:53:24 Age [y:d:h:m:s]: 02:066:13:16:12
Block: 898538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567247 RingCT/type: yes/0
Extra: 014285b1ea165c5a24ba1d47518361647c1a8cd59a4e432e014c0d2d1169703f8b021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.646800863000 dcy

stealth address amount amount idx
00: 368647a6783449969c1a148e9171f6de05dd9faa96eb51b1765b78abdc9e7e0e 0.646800863000 1354959 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": 898548, "vin": [ { "gen": { "height": 898538 } } ], "vout": [ { "amount": 646800863, "target": { "key": "368647a6783449969c1a148e9171f6de05dd9faa96eb51b1765b78abdc9e7e0e" } } ], "extra": [ 1, 66, 133, 177, 234, 22, 92, 90, 36, 186, 29, 71, 81, 131, 97, 100, 124, 26, 140, 213, 154, 78, 67, 46, 1, 76, 13, 45, 17, 105, 112, 63, 139, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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