Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11aacfc11bac57e32ebdf70f751250f10a501a4b703da6e4829313de962202c5

Tx prefix hash: 54cf5b695f91debfecbd77e8e409567f1aa24301545386cbdf780aef42ff3b65
Tx public key: 3ea99ebf6e88755cef20a77acd16ec8aa71f08e9573065a8906938eae75e098c
Timestamp: 1703190816 Timestamp [UCT]: 2023-12-21 20:33:36 Age [y:d:h:m:s]: 01:177:22:13:05
Block: 918194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388231 RingCT/type: yes/0
Extra: 013ea99ebf6e88755cef20a77acd16ec8aa71f08e9573065a8906938eae75e098c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc79933e2a9cc1e18953c9bb914d7f857480c612e03b0bc571a69eea1c8b6db5 0.600000000000 1375836 of 15

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": 918204, "vin": [ { "gen": { "height": 918194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc79933e2a9cc1e18953c9bb914d7f857480c612e03b0bc571a69eea1c8b6db5" } } ], "extra": [ 1, 62, 169, 158, 191, 110, 136, 117, 92, 239, 32, 167, 122, 205, 22, 236, 138, 167, 31, 8, 233, 87, 48, 101, 168, 144, 105, 56, 234, 231, 94, 9, 140, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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