Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e6ced80a1ae750084be1d7c1176bc5f77926fff807bc13e7f2c5b99751aa08

Tx prefix hash: 4de4d49d4808b43f3f0e7700095c490c48276ff61b1657a7e448ac4f07887796
Tx public key: 410016145e38bb5015ed6f94e97054e826f3c5ce03119926b4fc2c5e5f482bbc
Timestamp: 1699686572 Timestamp [UCT]: 2023-11-11 07:09:32 Age [y:d:h:m:s]: 01:073:04:30:27
Block: 889151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313672 RingCT/type: yes/0
Extra: 01410016145e38bb5015ed6f94e97054e826f3c5ce03119926b4fc2c5e5f482bbc02110000000333af99f4000000000000000000

1 output(s) for total of 0.694822114000 dcy

stealth address amount amount idx
00: 83eca341772d59967295e735a3e961b33f07fae7cac6b2f26b1494b7489748ad 0.694822114000 1345128 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": 889161, "vin": [ { "gen": { "height": 889151 } } ], "vout": [ { "amount": 694822114, "target": { "key": "83eca341772d59967295e735a3e961b33f07fae7cac6b2f26b1494b7489748ad" } } ], "extra": [ 1, 65, 0, 22, 20, 94, 56, 187, 80, 21, 237, 111, 148, 233, 112, 84, 232, 38, 243, 197, 206, 3, 17, 153, 38, 180, 252, 44, 94, 95, 72, 43, 188, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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