Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b470f48759b26556509219db3ab9d27cc2b06f10752d972541c3af16b64c4e4

Tx prefix hash: b31adf7441177f7d76b18ff6c39a9a843e35ff4f86a4b44e6dce128e7984ef88
Tx public key: 2a96fd7f796e75e0b4735d142daff85a51c11746b80bb34dc54f25c734b64215
Timestamp: 1663429511 Timestamp [UCT]: 2022-09-17 15:45:11 Age [y:d:h:m:s]: 02:183:19:46:31
Block: 589979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 652695 RingCT/type: yes/0
Extra: 012a96fd7f796e75e0b4735d142daff85a51c11746b80bb34dc54f25c734b64215021100000004faf35c9c000000000000000000

1 output(s) for total of 6.810119544000 dcy

stealth address amount amount idx
00: 4bd90b62f39bb67a4cc1f3cfbd6baeb337d9fd5c324ca214367fac457d6a5715 6.810119544000 1024348 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": 589989, "vin": [ { "gen": { "height": 589979 } } ], "vout": [ { "amount": 6810119544, "target": { "key": "4bd90b62f39bb67a4cc1f3cfbd6baeb337d9fd5c324ca214367fac457d6a5715" } } ], "extra": [ 1, 42, 150, 253, 127, 121, 110, 117, 224, 180, 115, 93, 20, 45, 175, 248, 90, 81, 193, 23, 70, 184, 11, 179, 77, 197, 79, 37, 199, 52, 182, 66, 21, 2, 17, 0, 0, 0, 4, 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