Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d36657c0e4baea52a76c80736808f9ebb91b456d37f619950b902ed9f823c6a

Tx prefix hash: f7d9f05fc08c84caedcc88b8153b0c515812179a4b27435adb145e1c70c98020
Tx public key: 761395a84ac272e499e90ae52c58072c8b4d3fd4182b89c7bed14d22358c74ad
Timestamp: 1731501710 Timestamp [UCT]: 2024-11-13 12:41:50 Age [y:d:h:m:s]: 00:010:16:59:46
Block: 1152818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7665 RingCT/type: yes/0
Extra: 01761395a84ac272e499e90ae52c58072c8b4d3fd4182b89c7bed14d22358c74ad021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7936d3d79614803d763ac706ff463d4d0acb5c2cc8f8e2364c016f54e9abf430 0.600000000000 1638423 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": 1152828, "vin": [ { "gen": { "height": 1152818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7936d3d79614803d763ac706ff463d4d0acb5c2cc8f8e2364c016f54e9abf430" } } ], "extra": [ 1, 118, 19, 149, 168, 74, 194, 114, 228, 153, 233, 10, 229, 44, 88, 7, 44, 139, 77, 63, 212, 24, 43, 137, 199, 190, 209, 77, 34, 53, 140, 116, 173, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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