Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 322fff5a1b8c1047daebcee681899a743f3d0aa18bf6ac5f33a1e96aa4727910

Tx prefix hash: 4550ff2d4cd28597354f5b9831feaaec486ed9285380128dc775dccc9b95ceb2
Tx public key: 3be38bca75c03768a5b24fb82b205b2a47ca10aa10d6b033a65351c7242e9665
Timestamp: 1704119266 Timestamp [UCT]: 2024-01-01 14:27:46 Age [y:d:h:m:s]: 01:102:09:19:01
Block: 925890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334285 RingCT/type: yes/0
Extra: 013be38bca75c03768a5b24fb82b205b2a47ca10aa10d6b033a65351c7242e9665021100000008e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f720ed7b3c12f49ae1bbd4908876e79d8db8fbaf60760a27681a8721a777cd27 0.600000000000 1383660 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": 925900, "vin": [ { "gen": { "height": 925890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f720ed7b3c12f49ae1bbd4908876e79d8db8fbaf60760a27681a8721a777cd27" } } ], "extra": [ 1, 59, 227, 139, 202, 117, 192, 55, 104, 165, 178, 79, 184, 43, 32, 91, 42, 71, 202, 16, 170, 16, 214, 176, 51, 166, 83, 81, 199, 36, 46, 150, 101, 2, 17, 0, 0, 0, 8, 224, 133, 50, 182, 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